Data Quality Fundamentals by Barr Moses Lior Gavish and Molly Vorwerck

Author:Barr Moses, Lior Gavish, and Molly Vorwerck
Language: eng
Format: mobi, epub
Publisher: O'Reilly Media, Inc.
Published: 2022-09-08T00:00:00+00:00

Resolution

Once you identify that something has gone awry and understand its initial impact, the next step (sometimes even before root cause analysis) is to fix the issue and communicate next steps to the proper stakeholders. This could be as easy as pausing your data pipelines or models and rerunning them, but since data can break for millions of reasons, this often involves a fair amount of troubleshooting.

In many cases, there may be an “initial resolution” (i.e., pause or “circuit break” a pipeline—recall we looked at circuit breaking in Chapter 3) and a “final resolution,” in other words, implement a more permanent solution that addresses the underlying cause of the data downtime incident. Throughout this process, it’s important to communicate the status of the incident in a dedicated Slack channel, email chain, Wiki site, Google Document, JIRA workflow, or other collaboration tool that makes it easy for various stakeholders to keep track of the current state of affairs.

After the incident is fixed, whether through changes to the code, data, or operational environment, teams should communicate next steps to the affected parties and in the coming days, schedule a postmortem.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.